Conversation
|
The following pipelines have been queued for testing: |
| -MaximumRetryCount 3 | ||
| } | ||
|
|
||
| function Get-GitHubIssues { |
There was a problem hiding this comment.
Do you use this API to get all issues with particular labels?
If so, can we have the right API name to indicate it is about labels as it is required parameters?
There was a problem hiding this comment.
Could you also add comments on what is the format for multi-labels?
There was a problem hiding this comment.
I actually prefer to have this as a single API that can support different level of filtering. Adding label to name will make it more specific than a general API. Currently implementation is based on label and creator but this can be enhanced to make them optional and support more query options.
There was a problem hiding this comment.
If support multi filters in this API, can we make labels as optional as well? Otherwise, people has no way to use this for authors only or for assignees only. It is currently working so specific for particular purpose.
|
Hello @azure-sdk! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
New API to get list of github issues based on labels and created user name. This API will be consumed by JS automation to file an issue for package deprecation and upgrade available warning if not already exists.